Status Update
Comments
ap...@google.com <ap...@google.com> #2
[Monorail components: -Platform>DevTools Blink>CSS]
ap...@google.com <ap...@google.com> #3
Steps:
---------
1. Launched chrome and opened devtools
2. Observed that able to add position and top rules.
Attached screen-cast for reference.
@Reporter: Could you please review the attached screen-cast and let us know if we missed anything from our end.
Requesting you to provide a sample URL/file that reproduce the issue, so that it would be really helpful in triaging the issue.
Thanks
ap...@google.com <ap...@google.com> #4
va...@google.com <va...@google.com>
tb...@google.com <tb...@google.com> #5
For more details visit
ap...@google.com <ap...@google.com> #6
[Monorail components: -Blink>CSS Platform>DevTools>Authoring]
yt...@google.com <yt...@google.com> #7
Thanks.!
va...@google.com <va...@google.com> #8
jb...@google.com <jb...@google.com> #9
ch...@huaqin.corp-partner.google.com <ch...@huaqin.corp-partner.google.com> #10
Sorry for the inconvenience if the bug really should have been left as Available.
For more details visit
se...@google.com <se...@google.com> #11
se...@google.com <se...@google.com> #12
ch...@huaqin.corp-partner.google.com <ch...@huaqin.corp-partner.google.com> #13
[Monorail components added to Component Tags custom field.]
ca...@google.com <ca...@google.com> #14
i got ccache: error: Failed to create directory /home/caveh/.cache/ccache/tmp: Permission denied
as i was setting up a repo on a fresh gLinux install,
so something is still not right with the ownerships.
something running as root creates those directories during repo setup... and it's game over.
ca...@google.com <ca...@google.com> #16
i don't think that's sufficient because the whole .cache tree was owned by root. lots of dirs and files :(
i'm creating a 2nd repo on the same machine - kind of curious if this only happens on the 1st repo creation on a new machine or all repo creations.
ca...@google.com <ca...@google.com> #17
[brya] $ l -d
drwxr-xr-x 11 caveh 4.0K Dec 15 16:45 ./
[brya] $ l -d .cache
drwxr-xr-x 3 root 4.0K Dec 15 15:48 .cache/
[brya] $ find .cache -user ${USER} -ls
49939140 4 drwxrwxr-x 4 caveh primarygroup 4096 Dec 15 15:48 .cache/cros/chromite/common
49939141 4 drwxrwxr-x 2 caveh primarygroup 4096 Dec 15 15:48 .cache/cros/chromite/common/staging
[brya] $ find .cache -user root | wc
4137 4137 433300
[brya] $
full list attached.
to...@google.com <to...@google.com> #18
I just hit this today. I ran a repo sync
on a machine where I had not done so in a long time. I was getting errors about the Python version in the chroot being out of date, which prevented me from running update_chroot
. I nuked the chroot and recreated it with cros_sdk --replace
. At that point ~/.cache
was owned by root
as others have mentioned:
(chroot) $ ls -lah $HOME/.cache
total 12K
drwxr-xr-x 3 root root 4.0K Feb 8 11:43 .
drwxr-xr-x 6 myuser primarygroup 4.0K Feb 8 13:27 ..
drwxr-xr-x 3 root root 4.0K Feb 8 11:43 cros
The chown
workaround in
ch...@huaqin.corp-partner.google.com <ch...@huaqin.corp-partner.google.com> #19
Today I tast run the test suite in
Description
let's switch the fallback cache dir from /tmp/chromeos-cache/ to ~/.cache/cros/chromite/