🚨 Error: failed to build: amp-experiment#1 Experiment amp-experiment-1.0 is not enabled.

[ampprojectbot]

Details

Error report: link
First seen: Jun 19, 2019
Frequency: ~ 1,108/day

Stacktrace

Error: failed to build: amp-experiment#1 Experiment amp-experiment-1.0 is not enabled.
    at message (src/log.js:710:22)
    at src/log.js:316:8
    at src/log.js:330:36
    at TAG (src/service/resource.js:32:12)
    at reason (src/service/resource.js:351:44)

Notes

@dvoytenko modified src/log.js:709-723 in #2597 (Mar 15, 2016)
@rsimha modified src/log.js:315-318 in #21212 (May 16, 2019)
@erwinmombay modified src/log.js:330-331 in #6581 (Dec 20, 2016)
@dvoytenko modified src/service/resource.js:31-74 in #3544 (Jun 14, 2016)
@rsimha modified src/service/resource.js:351-354 in #21212 (May 16, 2019)

Seen in:

• 06-11 Control (2352+3)
• 06-11 Nightly-Control (2352+3)
• 06-11 Stable (2352+3)
• 06-18 Experiment-B (0239+2)
• 06-18 Experimental (0239+2)
• +2 more

/cc @ampproject/release-on-duty

[dreamofabear]

@ampproject/wg-analytics Seems like a lot of errors for an unreleased extension. Did an origin trial expire?

[zhouyx]

Agreed could be an origin trial expiration. Is this reported as user errors?

[dreamofabear]

No, it's thrown from buildCallback. We probably just need to add a separate .catch() for the origin trial check.

[zhouyx]

I see. https://github.com/ampproject/amphtml/blob/master/extensions/amp-experiment/1.0/amp-experiment.js#L80

An easier way is to return early without throwing an error. I'll create a quick fix, we can safely ignore this error in the meantime.