Issue 1339761 in chromium: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.

[nagasudhak via monorail]

Status: Untriaged
Owner: ----
CC: nyerr...@chromium.org, pmad...@chromium.org
Labels: Inhouse-HYD-Reported FoundIn-103 FoundIn-104 FoundIn-105 M-105 RegressedIn-103 Target-103 Target-104 Target-105
Components: Internals>Flags Internals>Flags>Expired
OS: Linux Windows Mac
Pri: 1
Type: Bug-Regression

New issue 1339761 by nagas...@chromium.org: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761

Chrome Version : 104.0.5112.27 (Official Build) (x86_64)
997fdb0a8c451b5f1a56ad1ae5f92feaf2f63ac0-refs/branch-heads/5112@{#326}

OS : Win (10, 11), Mac(13.0, 11.6, 10.15.7) and Linux 18.04.5 LTS

Steps to reproduce:

1.Launch chrome, open NTP and Navigate to “chrome://flags” Page.
2.Enable the "#temporary-unexpire-flags-m103” & "#temporary-unexpire-flags-m102” flags.
3.Search for the "#chrome-tips-in-main-menu” flag.

Actual Result : "#chrome-tips-in-main-menu” flag missing in chrome flags.

Expected Result : "#chrome-tips-in-main-menu” flag should be there in chrome flags

This is a Regression Issue broken in M103 and below is the Per-revision Bisect info,

Good Build : 102.0.5005.0 (Revision : 992738 )
Bad Build : 103.0.5006.0 (Revision : 993115)

You are probably looking for a change made after 992829 (known good), but no later than 992830 (first known bad).

CHANGELOG URL:

The script might not always return single CL as suspect as some perf builds might get missing due to failure.

https://chromium.googlesource.com/chromium/src/+log/5c4a15cd72d204b2843a48efdfa96091567013fd..8446c149cea2b6d8342d559c57ca7fea269ac2bd

Suspect : https://chromium.googlesource.com/chromium/src/+/8446c149cea2b6d8342d559c57ca7fea269ac2bd

Seems this is not related to the Issue. Requesting someone from Devteam, could you please take a look into this issue and please help us in assigning it to the right owner.

Note:
1.Issue is also repro on Stable #103.0.5060.53, Beta #104.0.5112.20, and Dev #104.0.5112.20

Kindly refer the Screen shot's given below,

Thank You !

Attachments:
Actual Result.png 86.2 KB
Expected Result.png 157 KB

--
You received this message because:
1. You are auto-CC'd on all issues in component Internals>Flags
2. You are auto-CC'd on all issues in component Internals>Flags>Expired

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment or make updates.

[jmukthavaram via monorail]

Updates:
Labels: ReleaseBlock-Stable

Comment #1 on issue 1339761 by jmukth...@chromium.org: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761#c1

Adding RBS for tracking. Please adjust/remove if it is intentional change.

[jmukthavaram via monorail]

Updates:
Labels: M-103

Comment #2 on issue 1339761 by jmukth...@chromium.org: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761#c2

(No comment was entered for this change.)

[jmukthavaram via monorail]

Updates:
Owner: dfr...@chromium.org
Status: Assigned

Comment #4 on issue 1339761 by jmukth...@chromium.org: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761#c4

With reference to Issue 1174324 - assigning to dev for more inputs on this .

[avi via monorail]

Comment #5 on issue 1339761 by a...@chromium.org: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761#c5

Note that #chrome-tips-in-main-menu expired in M100. It is expected that the temporary unexpire wouldn’t work.

[songsuk via monorail]

Updates:
Labels: OS-Chrome

Comment #6 on issue 1339761 by son...@google.com: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761#c6

able to reproduce it on 103.0.5060.64(14816.82.0) -kefka

[songsuk via monorail]

Updates:
Cc: dga...@google.com chchak...@google.com

Comment #7 on issue 1339761 by son...@google.com: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761#c7

(No comment was entered for this change.)

[dgagnon via monorail]

Comment #8 on issue 1339761 by dga...@google.com: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761#c8

Per comment #5, it seems this expired as expected.

songsuk@ - can you confirm that this issue reproduces in M101? If yes, then we can remove the ReleaseBlock-Stable label.

[songsuk via monorail]

Comment #9 on issue 1339761 by son...@google.com: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761#c9

able to reproduce the issue on 14695.107.0/102.0.5005.125(Atlas). Will check it on M101.

[dgagnon via monorail]

Updates:
Labels: -ReleaseBlock-Stable

Comment #10 on issue 1339761 by dga...@google.com: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761#c10

Since this is reproducing on M102, I will remove the Stable blocker - we don't block future milestones if the issue is already affecting previous milestones: go/chromeos-release-blockers#what-are-not-release-blocking-issues

[dgagnon via monorail]

Updates:
Labels: ReleaseBlock-Stable

Comment #11 on issue 1339761 by dga...@google.com: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761#c11

Adding the blocker back so that Browser can decide if it will block any OS on their side (since this affects more than ChromeOS).

[songsuk via monorail]

Comment #12 on issue 1339761 by son...@google.com: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761#c12

#chrome-tips-in-main-menu is NOT available on chrome://flags in 101.0.4951.64, 103.0.5060.66, 104.0.5112.27- Linux (debian 5.7.17-1rodete4)

[sbalamuthiah via monorail]

Updates:
Cc: neh...@google.com puccha...@chromium.org sbalam...@google.com sriniv...@google.com pbom...@chromium.org

Comment #13 on issue 1339761 by sbalam...@google.com: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761#c13

Windows 10/11[Prajakta/Soundarya], MacOS 12.4[Narayana]

- Chrome Version: 103.0.5060.66
Disabled #temporary-unexpire-flags-m101, #temporary-unexpire-flags-m101 flags, chrome-tips-in-main-menu flag IS NOT available

- Chrome Version: 104.0.5112.27
Disabled #temporary-unexpire-flags-m102, #temporary-unexpire-flags-m103 flags, chrome-tips-in-main-menu flag IS NOT available

- chrome Version: 101.0.4951.64
Disabled "#temporary-unexpire-flags-m99” & "#temporary-unexpire-flags-m100; chrome-tips-in-main-menu flag IS available

[srinivassista via monorail]

Comment #15 on issue 1339761 by sriniv...@google.com: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761#c15

This should not block M103, flags expire and that is per intended work flow, If this flag needs to be unexpired, then engineers would need to add back to flags file and merge to M103,. But this flag expired in M101/102 and didnt create any issues, so i am confused why this is impacting users now?, We will not block stable for this issue

[dfried via monorail]

Updates:
Labels: -ReleaseBlock-Stable

Comment #16 on issue 1339761 by dfr...@google.com: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761#c16

Yes, this is known; we let the experiment expire while we were waiting for localization of the tips page and will restart the experiment when we are satisfied it is in shape to ship.

Thanks for the heads-up.

[dfried via monorail]

Updates:
Cc: dfr...@chromium.org mman...@chromium.org aj...@chromium.org

Comment #17 on issue 1339761 by dfr...@chromium.org: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761#c17

Issue 1338126 has been merged into this issue.

[dfried via monorail]

Updates:
Status: WontFix

Comment #18 on issue 1339761 by dfr...@chromium.org: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761#c18

I'm going to deprecate this as there is no movement on the issue. If we do decide to bring it back, we'll reopen.

[avi via monorail]

Comment #19 on issue 1339761 by a...@chromium.org: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761#c19

OP, do you have a test plan that refers to this flag?

[vpranavi via monorail]

Updates:
Labels: M-120 OS-Lacros

Comment #20 on issue 1339761 by vpra...@google.com: Regression : "#chrome-tips-in-main-menu” flag missing in chrome flags.
https://bugs.chromium.org/p/chromium/issues/detail?id=1339761#c20

Hi,

C#19>>
As part of CrOS/LaCrOS Full Pass Testing we execute below test cases but chrome-tips flag is missing in chrome://flags, hence unable to perform execute these test cases :


1.28.1 Check that "Tips for Chrome" option is visible in wrench menu - https://testtracker.googleplex.com/efforts/testcase/detail/343089763?tp_id=25874&result=&environment=
1.28.3 Check the option in Incognito window - https://testtracker.googleplex.com/efforts/testcase/detail/343089764?tp_id=25874&result=&environment=
1.28.4.Check the option in any theme and background -https://testtracker.googleplex.com/efforts/testcase/detail/343089765?tp_id=25874&result=&environment=
1.28.5 Check the option in dark mode - https://testtracker.googleplex.com/efforts/testcase/detail/343089766?tp_id=25874&result=&environment=

Could you please confirm whether this missing flag is WAI.

Adding LaCrOS OS component and observed this issue on LaCrOS Beta M120.0.6099.28 using ash-chrome M120 Beta #120.0.6099.25/15662.16.0 on Guybrush(Dewatt) device

Attachments:
Screen recording 2023-11-24 3.00.29 PM.webm 13.3 MB