API: Start/end time range ignored in aggregation queries

[alkalinecoffee]

What did you do?
I created a singlestat panel in Grafana that shows the total number of 200-status responses (sample query: sum(http_request_duration_seconds_count{status=200})). The time period of the query result should reflect that specified by the time range for the entire dashboard.

What did you expect to see?
When a user selects a range of "last 1 hour", etc, they should see the total number of requests over their selected time period.

What did you see instead? Under which circumstances?
The results of my queries are always the total number of requests for all-time. While the start/end values in the query originating from Grafana appear correct (sample query below), it seems that the start/end values are simply ignored on the prometheus end.

query_range?query=sum(http_request_duration_seconds_count{status="200"})&start=1507224144&end=1507227744&step=120

Environment
Amazon Linux in AWS

• System information:

Linux 4.9.51-10.52.amzn1.x86_64 x86_64

• Prometheus version:

Note: Also tried on 1.7.1, same issue

prometheus, version 1.7.2 (branch: HEAD, revision: 22eadbe635528fa17b99a7635fed6b6018103042)
  build user:       root@05b1548df2cc
  build date:       20170926-16:41:43
  go version:       go1.8.3

[alkalinecoffee]

Nevermind--ended up being some weird caching issue on my end unrelated to prometheus.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.