Open Bug 1581098 Opened 5 years ago Updated 2 years ago

It's confusing that Fluent throws in automation but not in local builds

Categories

(Core :: Internationalization, defect, P3)

defect

Tracking

()

People

(Reporter: johannh, Unassigned)

References

Details

On about:certificate we have a missing translation that we know is going to be fixed in a certain bug which is somewhat stalled but that didn't bother us so far because it's just a warning and no negative impact on our users. We didn't know about https://searchfox.org/mozilla-central/rev/878bbf3cb8897a208454df27535f3522ab482cf2/intl/l10n/Localization.jsm#194

So now I spent some time investigating weird failures with text not showing up correctly in our tests. I saw the error being thrown about the localization missing in the failure log but, when I tried to reproduce on my local build, it all worked and there was only a warning. Sheepishly I didn't really ponder the difference between "error" in the failure log and "warning" in my Nightly console and assumed they were the same thing, since evidently it worked fine for me.

The fact that I categorically ruled out this "warning" as being the root cause of the failure caused me to spend a lot of time trying to go into other directions.

It would be nice if we could fail in local builds, at least, and maybe also add to a note to the failure that this will be an error in automation.

It would be nice if we could fail in local builds, at least, and maybe also add to a note to the failure that this will be an error in automation.

I'm ok with both!

The priority flag is not set for this bug.
:m_kato, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(m_kato)
Flags: needinfo?(m_kato)
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.